Portico Developer Guide
Batch Processing
Merchant batches may be handled by Portico for all merchants on all Authorization Platforms. Merchants processing on the GSAP-NA and GSAP-AP Authorization Platforms have the option to be set up for the host to manage their batch.
Portico supports Portico-based batch management for merchants processing on all Authorization Platforms. Portico-based batch management is the default configuration for a DeviceId. For merchants processing on the GSAP-NA and GSAP-AP Authorization Platforms, this is known to the host as HBMI. When Portico manages the batch, the POS can use the Portico API to manipulate transactions and batches. It can also request Portico to close a batch. However, the POS does not provide any additional details or updates in the close request itself and does not stream a batch to Portico.
Batches are maintained at the DeviceId level. If a site (merchant) has multiple DeviceIds, each is closed individually. If a DeviceId does not have an open batch, the next financial transaction will create a new open batch. This means that a CreditAccountVerify or CreditAuth request does not open a batch, but a CreditSale or CreditAddtoBatch would open a new batch.
Please note that due to the requirements for Portico to stream batch details to payment facilitators, payment facilitators and their submerchants must be set up for Portico-based batch management. Due to split batch management, the following merchant configurations require Portico-based batch management:
Batch information will be removed from Portico after 90 days.
Portico supports Host-based batch management for merchants processing on the GSAP-NA and GSAP-AP Authorization Platforms. This is known to the host as HBTI. With HBTI, the host manages and closes the batch at a specified time or as needed, for example, when a transaction count threshold has been met. There is no concept of a batch in Portico. Batch reports and the BatchClose request are not supported.
Please note that the DeviceId must be configured in Portico to properly enable HBTI.
The total amount of all transactions in a batch cannot exceed 9,999,999,999.99
Exchange: The Exchange host has not published a maximum batch size. For ideal batch management, maximum size should be less than 10,000 transactions.
GSAP-AP: The maximum Batch Size is limited to 900 transactions. Portico will return an error when this threshold is reached. No additional transactions can process until the current batch is closed.
GSAP-NA: The Maximum Batch Size is limited to 9,999 transactions. The GSAP host will return an error when this threshold is reached. No additional transactions can process until the current batch is closed.
GNAP-UK: Maximum batch size is 9,999 transactions
For Portico-based batch management, batch handling is custom to each Host Processor.
Exchange: Portico is the system of record for transactions, batches, and settlement details. During BatchClose, Portico streams the batch to the Exchange Host.
GSAP-AP: Portico is the system of record for transactions, batches, and settlement details. During BatchClose, Portico checks the batch count and batch total with the host. If the totals match, the batch is closed. If the totals do not match, Portico streams the batch to the host.
GSAP-NA: The GSAP-NA host is the system of record for transactions, batches, and settlement details. During BatchClose, Portico checks the batch count and batch total with the host. If the totals match, the batch is closed. If the totals do not match, Portico requests that the host force close the batch.
GNAP-UK: The GNAP host is the system of record for transactions, batches, and settlement details. During BatchClose, Portico sends the batch count and batch total with the host and closes the batch.
Planet Payment: Portico is the system of record for transactions, batches, and settlement details. During BatchClose, Portico checks the batch count and batch total with the host. If the totals match, the batch is closed. If the totals do not match, Portico uploads the batch to Planet Payment. Portico verifies the batch count and total with Planet Payment and closes the batch.
Most DeviceIds have one authorization host only. Merchants accepting DCC with Planet Payments have an authorization host for their domestic transactions and have Planet Payment host their DCC transactions. In this situation, the Portico DeviceId maintains separate counts and totals for domestic and DCC transactions. During batch close, Portico sends the appropriate settlement message to each host and manages the responses to close the batch successfully. If one host batch does not close, the batch will be in error status.
Merchants enabled for Planet Payment must have Portico-based batch management.